sbx: v0.38 release - #25707
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
This PR updates CLI reference YAML files (vendored/generated) and adds v0.38.0 release notes. One vendored file was edited directly, and the new release notes section has two style violations.
|
|
||
| ### Highlights | ||
|
|
||
| **Kit spec v2.** A new schema is available for authoring kits, with a clearer structure for setup, permissions, agent instructions, networking, and credentials. Use `schemaVersion: "2"` for new kits; existing v1 kits continue to load through the legacy path. See the [kit spec reference](https://docs.docker.com/ai/sandboxes/customize/kit-reference/#schema-versions) for migration details. |
There was a problem hiding this comment.
[MEDIUM] Bold used for feature name, not a UI element
The style guide restricts bold to UI elements (buttons, menus, field labels). "Kit spec v2." is a feature name, not a UI element — remove the bold formatting and consider using a plain subheading (####) or integrating the text directly into the paragraph.
|
|
||
| **Kit spec v2.** A new schema is available for authoring kits, with a clearer structure for setup, permissions, agent instructions, networking, and credentials. Use `schemaVersion: "2"` for new kits; existing v1 kits continue to load through the legacy path. See the [kit spec reference](https://docs.docker.com/ai/sandboxes/customize/kit-reference/#schema-versions) for migration details. | ||
|
|
||
| **MCP management is now a first-class feature.** Register remote or local MCP servers once with `sbx mcp`, then reuse them across supported agents and sandboxes through a built-in MCP gateway. OAuth credentials stay on the host, and organizations can govern server registration and tool calls with Cedar policies. See the [MCP gateway documentation](https://docs.docker.com/ai/sandboxes/mcp-gateway/). |
There was a problem hiding this comment.
[MEDIUM] Bold for feature name + marketing language
Two style issues on this line:
- "MCP management is now a first-class feature." uses bold for a feature name, not a UI element — bold is only for UI elements per the style guide.
- "first-class feature" is marketing language. The style guide says to describe what something does, not label it with promotional descriptors.
Suggested rewrite: Remove the bold lead-in and lead with the functional description directly — for example: "MCP management is built in. Register remote or local MCP servers once with sbx mcp..."
| description: |- | ||
| Remove a network rule by rule ID, resource, or both. | ||
|
|
||
| --id takes the RULE_ID value shown by "sbx policy ls --wide" and |
There was a problem hiding this comment.
[HIGH] Vendored/generated CLI reference YAML edited directly
Files under data/sbx_cli/*.yaml are auto-generated from the upstream CLI source. Direct edits here will be overwritten on the next sync. This new --id documentation paragraph should be added upstream (in the CLI source) and synced back via the generation pipeline.
2 participants
Uh oh!
There was an error while loading. Please reload this page.